packages/browser/__tests__/unit/tracker.test.ts (1)

203-274: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Add a test for hasAttributionChanged's normalization logic.

Both new tests use clearly distinct identities, so the trim/case-insensitive-email normalization added in hasAttributionChanged (tracker.ts lines 371-378) is untested. Worth adding a case verifying that re-identifying with the same email in different casing/whitespace (or same trimmed userId/customerId) does not trigger an extra flush/attribution change.

it("does not flush when identify is called with the same normalized identity", async () => {
  const outlit = new Outlit({ publicKey: "pk_test", autoTrack: false, trackPageviews: false, trackForms: false, trackEngagement: false })
  outlit.enableTracking()
  outlit.identify({ email: "User-A@Example.com " })
  await outlit.flush()

  outlit.track("same_identity_event")
  outlit.identify({ email: "  user-a@example.com" }) // same identity, different case/whitespace
  await outlit.flush()

  const payloads = vi.mocked(global.fetch).mock.calls.map(([, options]) => JSON.parse(String(options?.body)))
  // Expect the track event and the re-identify to batch together in one flush call,
  // rather than being split by an unnecessary attribution-change flush.
  expect(payloads).toHaveLength(2)
})

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/browser/__tests__/unit/tracker.test.ts` around lines 203 - 274, Add
a test in the tracker unit-test suite covering hasAttributionChanged
normalization: identify with an email containing different casing and
surrounding whitespace, queue an event, then identify the same normalized email
and flush. Assert no extra attribution-change flush occurs by verifying both
actions remain in the expected single post-initial-identification payload, while
preserving the existing distinct-identity tests.